Skip to content

DEVOPS-1066: use newer pr_jira_actions workflow#139

Merged
sebhmg merged 1 commit intodevelopfrom
DEVOPS-1066
Apr 17, 2026
Merged

DEVOPS-1066: use newer pr_jira_actions workflow#139
sebhmg merged 1 commit intodevelopfrom
DEVOPS-1066

Conversation

@sebhmg
Copy link
Copy Markdown

@sebhmg sebhmg commented Apr 17, 2026

DEVOPS-1066 - use CI-tools v3 in all the repos

Copilot AI review requested due to automatic review settings April 17, 2026 17:03
@github-actions github-actions bot changed the title [DEVOPS-1066] use newer pr_jira_actions workflow DEVOPS-1066: use newer pr_jira_actions workflow Apr 17, 2026
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the repository’s PR-to-JIRA GitHub Actions integration to use the newer reusable workflow from MiraGeoscience/CI-tools, aligning PR event handling with the updated workflow interface.

Changes:

  • Switch workflow trigger from pull_request_target (opened only) to pull_request with additional PR event types.
  • Update reusable workflow reference from reusable-jira-pr_add_jira_summary.yml@v2 to reusable-jira-pr_actions.yml@v3.
  • Rename the job accordingly and adjust secrets ordering.
Comments suppressed due to low confidence (2)

.github/workflows/pr_jira_actions.yml:9

  • This workflow no longer restricts execution to the MiraGeoscience org (the previous job used if: startsWith(github.repository, 'MiraGeoscience/')). Other workflows that call MiraGeoscience/CI-tools (e.g., .github/workflows/issue_to_jira.yml) keep this guard to avoid running in upstream/forks where JIRA secrets may not exist. Consider reintroducing the repo/org check (or another explicit condition) so the job doesn’t run (and fail noisily) outside MiraGeoscience-owned repos.
    .github/workflows/pr_jira_actions.yml:7
  • This workflow dropped the top-level permissions: {} hardening that is used in other workflows in this repo (e.g., .github/workflows/security_scan.yml:20, .github/workflows/issue_to_jira.yml:7). Even though the job sets its own permissions, adding an explicit top-level permissions block helps avoid relying on repository-default GITHUB_TOKEN permissions and keeps the repo’s workflow security posture consistent.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@sebhmg sebhmg merged commit 831c9c7 into develop Apr 17, 2026
17 checks passed
@sebhmg sebhmg deleted the DEVOPS-1066 branch April 17, 2026 17:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants